feat: Add validate command - #307

What

Adds amp validate [ampYamlSourcePath] — validates an amp.yaml manifest without deploying it.

The path argument can be a directory containing amp.yaml/amp.yml or a path to the manifest file itself; it defaults to the current directory.

amp validate                    # validate ./amp.yaml
amp validate path/to/dir        # validate dir/amp.yaml
amp validate path/to/foo.yaml   # validate an explicitly named file
amp validate --project my-proj  # also check destinations & provider apps against the project

Flags:

• --strict — treat warnings as errors
• --skip-provider — skip provider-specific validation
• --skip-async — skip async error-prevention validation

Exits non-zero when validation fails, so it can gate CI. Output lists each error/warning with its rule, YAML path, line/column, and a suggestion when available.

How

Validation logic lives in the new amp-labs/amp-yaml-validator library (shared so the same rules can run client-side and server-side). The CLI supplies it with live data through the library's dependency-injection hooks:

• validate/catalog.go — a catalog.CatalogProvider backed by the live ("dynamic") provider catalog fetched from the public /v1/providers endpoint, so provider/module/capability checks stay current instead of relying on the catalog compiled into the connectors library. Fetched once per run and served from that snapshot.
• validate/checkers.go — DestinationChecker / ProviderAppChecker verify that destinations and provider apps referenced by the manifest actually exist in the project, backed by one-time snapshots from ListDestinations / ListProviderApps.
• request/api.go — new FetchProviderCatalog for the catalog endpoint (public, unauthenticated, not project-scoped; honors AMP_API_URL).
• files/zip.go — new FindManifestFile helper: explicit file paths are used as-is, directories are searched for the conventional manifest names.

Graceful degradation

The command never requires network or a project to be useful:

• No --project configured → destination and provider-app checks are skipped (the validator emits reminder warnings instead of hard errors).
• Catalog fetch fails (e.g. offline) → falls back to the catalog embedded in the connectors library.
• Destination/provider-app fetch fails → that checker is skipped (debug-logged), schema validation still runs.

Dependencies

Adds amp-labs/amp-yaml-validator and amp-labs/connectors (plus their transitive tree — AWS SDK v2, OpenTelemetry, etc. — all indirect).

Screenshots

Example of valid YAML:

Example of invalid YAML:

🤖 Generated with Claude Code